home *** CD-ROM | disk | FTP | other *** search
- Path: btree.is.brooktree.com!usenet
- From: sasha@brooktree.com (Alex Bakaev)
- Newsgroups: comp.lang.c++
- Subject: Re: MFC v.s. OWL class libraries
- Date: Mon, 22 Jan 1996 19:43:36 GMT
- Organization: Brooktree Corporation
- Message-ID: <4e0pap$b14@btree.brooktree.com>
- References: <4chen9$ldg@gold.datalytics.com> <4dld6f$9l5@news1.usa.pipeline.com>
- NNTP-Posting-Host: komissar.is.brooktree.com
-
- grantp@usa.pipeline.com(Pete) wrote:
-
- [deleted]
-
- >OWL is undeniably technically superior to MFC, but is more
- >difficult to use by Joe Bloe who's been programming all of
- >6 months now. Management knows this and (rightly so)
- >chooses MFC over OWL as their development tool. The
- >technical aspects of the class library are transparent in the
- >final product.
-
- Can not disagree more. Though on the surface it may seem like it is
- much simple to code using MFC it is only so for trivial cases. Once
- you have to implement something out of boundaries you are much better
- off using OWL. So unless your application's functionality does not go
- beyond Wizards, you are fine with MFC. With OWL you can do more and
- better - that's where techical superiority comes into play.
-
- Regards, Alex
-
-